Changes

Adds a metadata injector. It basically splits off socket functionality from mqtt_processor into its own file, and hides the metadata behind a flag.

Currently, the timers socketIO key:

{
  "topic": "BMS/Charging/Control",
  "last_change": "2025-01-18T02:40:09.521458544Z",
  "last_value": 0
}

Currently, the faults socketIO key (sample):

[
  {
    "node": "Bms",
    "name": "DCL_Enforce",
    "occured_at": "2025-01-18T02:39:36.972566Z",
    "last_seen": "2025-01-18T02:40:09.506620Z",
    "expired": false
  },
  {
    "node": "Bms",
    "name": "External_Can",
    "occured_at": "2025-01-18T02:39:36.972585Z",
    "last_seen": "2025-01-18T02:40:09.506653Z",
    "expired": false
  },
  {
    "node": "Bms",
    "name": "Charge_Reading",
    "occured_at": "2025-01-18T02:39:36.972731Z",
    "last_seen": "2025-01-18T02:40:09.506750Z",
    "expired": false
  },
]

Currently

Notes

• The fault and timer re-use and buffering logic is shaky and uses some assumptions: A fault that does not broadcast in 8+ seconds is considered a new fault. A timer cannot be a fault. There will never be more than 25 concurrent faults (lol).
• Depends on [CANGEN] - Implement MPU Faults as bitwise Embedded-Base#225 for MPU faulting to be detected.

To Do

Any remaining things that need to get done

• Figure out what to do about latency sender

Checklist

• No merge conflicts
• All checks passing
• Screenshots of UI changes (see Screenshots section)
• Remove any non-applicable sections of this template
• Assign the PR to yourself
• No package-lock.json changes (unless dependencies have changed)
• Request reviewers & ping on Slack
• PR is linked to the ticket (fill in the closes line below)

Closes #223
Closes #207